Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 847a06da8d846de06f7ee5c6ff040b47a92a9fb729066a8e9349b58cf8024e08

Tx prefix hash: b159a6ca48ffb8aefd1b7db28b748dc8f1e8e806927349f2c5b47573f06fd4c2
Tx public key: 32c2686b3c5729636a7c1e7316382b222785d8edd6f96aaecb7c8dad599bb04d
Timestamp: 1701436827 Timestamp [UCT]: 2023-12-01 13:20:27 Age [y:d:h:m:s]: 01:050:07:20:35
Block: 903650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297301 RingCT/type: yes/0
Extra: 0132c2686b3c5729636a7c1e7316382b222785d8edd6f96aaecb7c8dad599bb04d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.622060185000 dcy

stealth address amount amount idx
00: 538444ec1a1d1bbfef6da7bd4bf8f00d297990e13bc423802bb42c6315b9e2d4 0.622060185000 1360337 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": 903660, "vin": [ { "gen": { "height": 903650 } } ], "vout": [ { "amount": 622060185, "target": { "key": "538444ec1a1d1bbfef6da7bd4bf8f00d297990e13bc423802bb42c6315b9e2d4" } } ], "extra": [ 1, 50, 194, 104, 107, 60, 87, 41, 99, 106, 124, 30, 115, 22, 56, 43, 34, 39, 133, 216, 237, 214, 249, 106, 174, 203, 124, 141, 173, 89, 155, 176, 77, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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