Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b003c9d87e8c7ddec225588a181fb5101c409cca913bdd98326f1f5c3df8456d

Tx prefix hash: b4631d2785f4a112ae88adda16fb21187a4be6101faf75a2566542c414b4e851
Tx public key: 1232a088cd6b3999619612740e15aee9c824a4fe97f1816c8ed439e63c5fafeb
Timestamp: 1582101611 Timestamp [UCT]: 2020-02-19 08:40:11 Age [y:d:h:m:s]: 05:281:14:55:30
Block: 68040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1352116 RingCT/type: yes/0
Extra: 011232a088cd6b3999619612740e15aee9c824a4fe97f1816c8ed439e63c5fafeb02110000000112c4732d000000000000000000

1 output(s) for total of 365.221252738000 dcy

stealth address amount amount idx
00: da5b892a37ed2a8b2b7926049c152738fedcba535a1ac02fc37e117dce483bae 365.221252738000 125328 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": 68050, "vin": [ { "gen": { "height": 68040 } } ], "vout": [ { "amount": 365221252738, "target": { "key": "da5b892a37ed2a8b2b7926049c152738fedcba535a1ac02fc37e117dce483bae" } } ], "extra": [ 1, 18, 50, 160, 136, 205, 107, 57, 153, 97, 150, 18, 116, 14, 21, 174, 233, 200, 36, 164, 254, 151, 241, 129, 108, 142, 212, 57, 230, 60, 95, 175, 235, 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