Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ade6ed0bee9fce1992caf35d3afd4ed7a8c2c167fdd76f4895b332b06435f0d4

Tx prefix hash: cc7486ef22ecce1d4eed25e70f92ab570d1b93e50c8c71412af9f8036eb72a9e
Tx public key: 762ef3a8bdf79d7e3e23f4ffc6b563308102ff7ce4d5aac506e11f1dc9d931ad
Timestamp: 1673934376 Timestamp [UCT]: 2023-01-17 05:46:16 Age [y:d:h:m:s]: 02:118:03:45:04
Block: 676506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606146 RingCT/type: yes/0
Extra: 01762ef3a8bdf79d7e3e23f4ffc6b563308102ff7ce4d5aac506e11f1dc9d931ad0211000000048b7b6602000000000000000000

1 output(s) for total of 3.519287433000 dcy

stealth address amount amount idx
00: 824ccdf66bd3e05d5630e86ed7ef623349a03b3f8814b882d163a387fa248cf3 3.519287433000 1118223 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": 676516, "vin": [ { "gen": { "height": 676506 } } ], "vout": [ { "amount": 3519287433, "target": { "key": "824ccdf66bd3e05d5630e86ed7ef623349a03b3f8814b882d163a387fa248cf3" } } ], "extra": [ 1, 118, 46, 243, 168, 189, 247, 157, 126, 62, 35, 244, 255, 198, 181, 99, 48, 129, 2, 255, 124, 228, 213, 170, 197, 6, 225, 31, 29, 201, 217, 49, 173, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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