Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b499619713fd2372cab1be3d255f7ef0ef9c2b33778b1625128426774a9ce5d7

Tx prefix hash: 0e55cf36c29cebff57c961411ac66541baa02135860072625917f5e302fbdc3a
Tx public key: 7070854d834703702d1509d2e4e7acab9c865e69e2137e9c0b7a5a7a2fb49907
Timestamp: 1626595141 Timestamp [UCT]: 2021-07-18 07:59:01 Age [y:d:h:m:s]: 03:130:15:02:48
Block: 296112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864887 RingCT/type: yes/0
Extra: 017070854d834703702d1509d2e4e7acab9c865e69e2137e9c0b7a5a7a2fb49907021100000014d2fc4d28000000000000000000

1 output(s) for total of 64.100072135000 dcy

stealth address amount amount idx
00: 2046cc2ff63585ca2326819a5cc97c0e1a3889b11befa746359f5020129f984d 64.100072135000 619954 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": 296122, "vin": [ { "gen": { "height": 296112 } } ], "vout": [ { "amount": 64100072135, "target": { "key": "2046cc2ff63585ca2326819a5cc97c0e1a3889b11befa746359f5020129f984d" } } ], "extra": [ 1, 112, 112, 133, 77, 131, 71, 3, 112, 45, 21, 9, 210, 228, 231, 172, 171, 156, 134, 94, 105, 226, 19, 126, 156, 11, 122, 90, 122, 47, 180, 153, 7, 2, 17, 0, 0, 0, 20, 210, 252, 77, 40, 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