Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2679ce13c26daddf62c8e716c3002ebe961d8c9546791fff76a6bac5d124ba15

Tx prefix hash: 6a4ccf6167e426889504c6c2303e37c55c389e7d71d39042bd4121ea6d76c861
Tx public key: 138e82e8d65906d37e35a8ac3e3d708440838c6c50e45bd1de355824a7c6f8f0
Timestamp: 1705305673 Timestamp [UCT]: 2024-01-15 08:01:13 Age [y:d:h:m:s]: 01:100:23:58:07
Block: 935708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333307 RingCT/type: yes/0
Extra: 01138e82e8d65906d37e35a8ac3e3d708440838c6c50e45bd1de355824a7c6f8f00211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0590c377d97b8d82f289e9d939df1ea8a49571d75e3a57680c2900802d052d5 0.600000000000 1393724 of 15

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": 935718, "vin": [ { "gen": { "height": 935708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0590c377d97b8d82f289e9d939df1ea8a49571d75e3a57680c2900802d052d5" } } ], "extra": [ 1, 19, 142, 130, 232, 214, 89, 6, 211, 126, 53, 168, 172, 62, 61, 112, 132, 64, 131, 140, 108, 80, 228, 91, 209, 222, 53, 88, 36, 167, 198, 248, 240, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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