Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8a79dc65954dd1c20e131566e3498f15d9720093d52a6e67e38d7c509af397a

Tx prefix hash: 7acb6489a540bca0bd8644553a79aac8fedd9c976e75e8970c75ffeeca5db920
Tx public key: 78c25a8feb06bbc9db4934bdef940d282c6c5b36e88710fd29cec75198858e8a
Timestamp: 1731718149 Timestamp [UCT]: 2024-11-16 00:49:09 Age [y:d:h:m:s]: 00:189:23:58:29
Block: 1154621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135652 RingCT/type: yes/0
Extra: 0178c25a8feb06bbc9db4934bdef940d282c6c5b36e88710fd29cec75198858e8a02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3b242311d82e122a9b8fb621a3d1b88cc8a98eda6e1648c3b6b060d08b69665 0.600000000000 1640234 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": 1154631, "vin": [ { "gen": { "height": 1154621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3b242311d82e122a9b8fb621a3d1b88cc8a98eda6e1648c3b6b060d08b69665" } } ], "extra": [ 1, 120, 194, 90, 143, 235, 6, 187, 201, 219, 73, 52, 189, 239, 148, 13, 40, 44, 108, 91, 54, 232, 135, 16, 253, 41, 206, 199, 81, 152, 133, 142, 138, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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