Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b0bca2ffcb3530fafaffa3aa4d1f0f17ddaba662d82781e4c7e73626e6c893

Tx prefix hash: 7ba4a60b52106e88fbab23692cb99a70f78c683d42a7d83ae1c2fed07cb8325d
Tx public key: 69839c7c36d3d2940d9ca00cc0c837eda763dc38293583af8972d913d8d55aa7
Timestamp: 1712831844 Timestamp [UCT]: 2024-04-11 10:37:24 Age [y:d:h:m:s]: 00:312:14:53:00
Block: 998101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223481 RingCT/type: yes/0
Extra: 0169839c7c36d3d2940d9ca00cc0c837eda763dc38293583af8972d913d8d55aa702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 140b728068b5d3f07761726f17478faf2c2da56248cff9c2524ec803777daec7 0.600000000000 1458543 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": 998111, "vin": [ { "gen": { "height": 998101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "140b728068b5d3f07761726f17478faf2c2da56248cff9c2524ec803777daec7" } } ], "extra": [ 1, 105, 131, 156, 124, 54, 211, 210, 148, 13, 156, 160, 12, 192, 200, 55, 237, 167, 99, 220, 56, 41, 53, 131, 175, 137, 114, 217, 19, 216, 213, 90, 167, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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