Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d98c744eda6bcaf3e8fb76e799643c9ff843e8e1aadbf6cc8a6e48e4133380

Tx prefix hash: 0001d64976cfa62211fdb76b7c823df6b7f4ea6f8d5f816c2c7c8b11de116234
Tx public key: ef3760aa22813e17f317f9d798748ebab542f0fbee4ecd0f8778f41df1ca5d99
Timestamp: 1700747336 Timestamp [UCT]: 2023-11-23 13:48:56 Age [y:d:h:m:s]: 01:092:19:52:49
Block: 897937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327480 RingCT/type: yes/0
Extra: 01ef3760aa22813e17f317f9d798748ebab542f0fbee4ecd0f8778f41df1ca5d990211000000024b8f5122000000000000000000

1 output(s) for total of 0.649773438000 dcy

stealth address amount amount idx
00: 7e4c38e05b4b0264183afc562dd4420afd2400b5b0589e29d1cf39f4be3ea35d 0.649773438000 1354334 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": 897947, "vin": [ { "gen": { "height": 897937 } } ], "vout": [ { "amount": 649773438, "target": { "key": "7e4c38e05b4b0264183afc562dd4420afd2400b5b0589e29d1cf39f4be3ea35d" } } ], "extra": [ 1, 239, 55, 96, 170, 34, 129, 62, 23, 243, 23, 249, 215, 152, 116, 142, 186, 181, 66, 240, 251, 238, 78, 205, 15, 135, 120, 244, 29, 241, 202, 93, 153, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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