Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4731003a1854bf11738cb1a265c3c7bb1ea8a958f5d6d28f9b3dff612cf0413e

Tx prefix hash: 66ddd207dac1627b77035ec99f687ca7a44b566e32c9a4141455cb5e442953c0
Tx public key: ae0cd69483b4d3029c12345f822a4a29cf868144882e34d605a642cd5dc18a7d
Timestamp: 1731649345 Timestamp [UCT]: 2024-11-15 05:42:25 Age [y:d:h:m:s]: 00:154:06:37:47
Block: 1154037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110102 RingCT/type: yes/0
Extra: 01ae0cd69483b4d3029c12345f822a4a29cf868144882e34d605a642cd5dc18a7d021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36793c64f793664b0d8826cc2b75159b7fac7a70b6465c83e361e3b78ee46a7f 0.600000000000 1639648 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": 1154047, "vin": [ { "gen": { "height": 1154037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36793c64f793664b0d8826cc2b75159b7fac7a70b6465c83e361e3b78ee46a7f" } } ], "extra": [ 1, 174, 12, 214, 148, 131, 180, 211, 2, 156, 18, 52, 95, 130, 42, 74, 41, 207, 134, 129, 68, 136, 46, 52, 214, 5, 166, 66, 205, 93, 193, 138, 125, 2, 17, 0, 0, 0, 8, 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