Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5683b11816e09781d37d2c0c100a89f6f285fe6194f4ec07368892841f8cb309

Tx prefix hash: 033610d641d8322910f53f181596e531d39fdc8fc62c17f4339ec4011f8793ed
Tx public key: 73b4c5d81747d8faa920978e26afd75e445edc3f3337bfc33e84e962aa5b3710
Timestamp: 1717788878 Timestamp [UCT]: 2024-06-07 19:34:38 Age [y:d:h:m:s]: 00:328:03:17:07
Block: 1039225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234519 RingCT/type: yes/0
Extra: 0173b4c5d81747d8faa920978e26afd75e445edc3f3337bfc33e84e962aa5b37100211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dbbbc32b3c1ec9a74ec5636e2df391aa5d9112d35bf395b4874cb3102712b21 0.600000000000 1507852 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": 1039235, "vin": [ { "gen": { "height": 1039225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dbbbc32b3c1ec9a74ec5636e2df391aa5d9112d35bf395b4874cb3102712b21" } } ], "extra": [ 1, 115, 180, 197, 216, 23, 71, 216, 250, 169, 32, 151, 142, 38, 175, 215, 94, 68, 94, 220, 63, 51, 55, 191, 195, 62, 132, 233, 98, 170, 91, 55, 16, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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