Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9a813507e44cf142f57f9560829315ce6bb9d68bfd8a700f01ec20faf2ac77

Tx prefix hash: 0e2f7d3291dc901efb872139ad4f3b510d86199148cf2eff3187ed4573891a68
Tx public key: f1be2f95962e00d954d77ca408e20982fe383ea08851eadee240e138581af7e8
Timestamp: 1700948161 Timestamp [UCT]: 2023-11-25 21:36:01 Age [y:d:h:m:s]: 01:170:11:53:01
Block: 899605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383047 RingCT/type: yes/0
Extra: 01f1be2f95962e00d954d77ca408e20982fe383ea08851eadee240e138581af7e8021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.641556893000 dcy

stealth address amount amount idx
00: 01706f76fb09cec1d9436a3f53b37956bed370ba8ef1f520df9c979a5e6a3c78 0.641556893000 1356064 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": 899615, "vin": [ { "gen": { "height": 899605 } } ], "vout": [ { "amount": 641556893, "target": { "key": "01706f76fb09cec1d9436a3f53b37956bed370ba8ef1f520df9c979a5e6a3c78" } } ], "extra": [ 1, 241, 190, 47, 149, 150, 46, 0, 217, 84, 215, 124, 164, 8, 226, 9, 130, 254, 56, 62, 160, 136, 81, 234, 222, 226, 64, 225, 56, 88, 26, 247, 232, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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