Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c650707ee07c9544ab9fc60b091139478f5ce70f8faad4e8d1d48f6a01fc044

Tx prefix hash: d579da0b2f407683559cb45bf73b26283ac7c96910268027ce1a5920117b1c0e
Tx public key: 2f99d065221a126a4414756bed8b03c30b66e5e08523dece7c23fb50c6cdf71a
Timestamp: 1583855416 Timestamp [UCT]: 2020-03-10 15:50:16 Age [y:d:h:m:s]: 05:038:13:53:26
Block: 79892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183326 RingCT/type: yes/0
Extra: 012f99d065221a126a4414756bed8b03c30b66e5e08523dece7c23fb50c6cdf71a021100000001c48ea382000000000000000000

1 output(s) for total of 333.645621093000 dcy

stealth address amount amount idx
00: 22f0ebf8c100675202e2061becb11e5950945b2cc0a84b14af62f7d4da92a87b 333.645621093000 146184 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": 79902, "vin": [ { "gen": { "height": 79892 } } ], "vout": [ { "amount": 333645621093, "target": { "key": "22f0ebf8c100675202e2061becb11e5950945b2cc0a84b14af62f7d4da92a87b" } } ], "extra": [ 1, 47, 153, 208, 101, 34, 26, 18, 106, 68, 20, 117, 107, 237, 139, 3, 195, 11, 102, 229, 224, 133, 35, 222, 206, 124, 35, 251, 80, 198, 205, 247, 26, 2, 17, 0, 0, 0, 1, 196, 142, 163, 130, 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