Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f86faad380e892a527caa3a2af1374cc1ddebc27b9e7683da32648ee964fae9

Tx prefix hash: 980861f371f03b0993fab356d10669986abf193d0141c9f3800fcb39eac7d22f
Tx public key: bd18bab5e4fc2a5e95a2160e0835fb51a6e8442bdf03aa94744da2213e21fecd
Timestamp: 1582332720 Timestamp [UCT]: 2020-02-22 00:52:00 Age [y:d:h:m:s]: 05:253:18:23:13
Block: 69786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1332345 RingCT/type: yes/0
Extra: 01bd18bab5e4fc2a5e95a2160e0835fb51a6e8442bdf03aa94744da2213e21fecd02110000000112c4732d000000000000000000

1 output(s) for total of 360.394630594000 dcy

stealth address amount amount idx
00: 20d9cfcd77d473c3d5670484bc725a178c26e3c86f237d05a1aa90931e9d47e8 360.394630594000 128797 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": 69796, "vin": [ { "gen": { "height": 69786 } } ], "vout": [ { "amount": 360394630594, "target": { "key": "20d9cfcd77d473c3d5670484bc725a178c26e3c86f237d05a1aa90931e9d47e8" } } ], "extra": [ 1, 189, 24, 186, 181, 228, 252, 42, 94, 149, 162, 22, 14, 8, 53, 251, 81, 166, 232, 68, 43, 223, 3, 170, 148, 116, 77, 162, 33, 62, 33, 254, 205, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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