Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378b6f5f8eedeceba6a2e2da5aea9dbaf727eaec4d31738611ca0284e47cdb82

Tx prefix hash: a24f68c4233d468cae11e50ff03eb2c4f6a2ec937e47e2cfc24cd960e0e03644
Tx public key: b49c737c05bc54f1038973eea3b5b8384865a3329562c672e64d750975d0962d
Timestamp: 1577822123 Timestamp [UCT]: 2019-12-31 19:55:23 Age [y:d:h:m:s]: 05:100:18:52:22
Block: 35978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221790 RingCT/type: yes/0
Extra: 01b49c737c05bc54f1038973eea3b5b8384865a3329562c672e64d750975d0962d021100000010feadaf7f000000000000000000

1 output(s) for total of 466.434648919000 dcy

stealth address amount amount idx
00: 10c3e812b83d2da4f3567ba8f56ded0982055663e556f6e95f3bae438265f18a 466.434648919000 60786 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": 35988, "vin": [ { "gen": { "height": 35978 } } ], "vout": [ { "amount": 466434648919, "target": { "key": "10c3e812b83d2da4f3567ba8f56ded0982055663e556f6e95f3bae438265f18a" } } ], "extra": [ 1, 180, 156, 115, 124, 5, 188, 84, 241, 3, 137, 115, 238, 163, 181, 184, 56, 72, 101, 163, 50, 149, 98, 198, 114, 230, 77, 117, 9, 117, 208, 150, 45, 2, 17, 0, 0, 0, 16, 254, 173, 175, 127, 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