Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f8bceae2b4c5ee6029db23b2988ab9f10c3aa526df0eeb9cf9b602d816a462

Tx prefix hash: 44e98c3ce03b73af7be60c8a4d144160a9aaaf45d137e3e738e20211b4e8bc87
Tx public key: b6cca61ad205d00539e9ed8e74514b0912a76dd8ade19ef6e1b6e3cc0e4c2862
Timestamp: 1712618661 Timestamp [UCT]: 2024-04-08 23:24:21 Age [y:d:h:m:s]: 01:205:22:37:45
Block: 996331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405880 RingCT/type: yes/0
Extra: 01b6cca61ad205d00539e9ed8e74514b0912a76dd8ade19ef6e1b6e3cc0e4c286202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d49580707ee64c62363e4afa9617938ffc2212a7b0c9c3f302cb919be9634f17 0.600000000000 1456749 of 15

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": 996341, "vin": [ { "gen": { "height": 996331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d49580707ee64c62363e4afa9617938ffc2212a7b0c9c3f302cb919be9634f17" } } ], "extra": [ 1, 182, 204, 166, 26, 210, 5, 208, 5, 57, 233, 237, 142, 116, 81, 75, 9, 18, 167, 109, 216, 173, 225, 158, 246, 225, 182, 227, 204, 14, 76, 40, 98, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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