Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a3dad5dcac45c473ab4269c4b705d5f8d8ab013e99dd6d81eb538214217a0b0f

Tx prefix hash: 929a875c3054c995616ab8c2d965c75db5f0f2448d958cd7986d676802cb967a
Tx public key: 9dca895b3b8fe62b510067ee7aaedd08dc429708eaccaac1210e88a28b07871a
Timestamp: 1657082164 Timestamp [UCT]: 2022-07-06 04:36:04 Age [y:d:h:m:s]: 02:181:13:33:41
Block: 537635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651119 RingCT/type: yes/0
Extra: 019dca895b3b8fe62b510067ee7aaedd08dc429708eaccaac1210e88a28b07871a0211000000194da16a3a000000000000000000

1 output(s) for total of 10.152949183000 dcy

stealth address amount amount idx
00: e27ab6380fd8835994d49757510af3f934769d3f84b1573d23644d527f978205 10.152949183000 967544 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 537645, "vin": [ { "gen": { "height": 537635 } } ], "vout": [ { "amount": 10152949183, "target": { "key": "e27ab6380fd8835994d49757510af3f934769d3f84b1573d23644d527f978205" } } ], "extra": [ 1, 157, 202, 137, 91, 59, 143, 230, 43, 81, 0, 103, 238, 122, 174, 221, 8, 220, 66, 151, 8, 234, 204, 170, 193, 33, 14, 136, 162, 139, 7, 135, 26, 2, 17, 0, 0, 0, 25, 77, 161, 106, 58, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8