Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 226fd0398473e14836c60ab7c110554c38c726d6ea5886c6de78c8fe3362958c

Tx prefix hash: b01089a57414be3c6e495e5a5fea4c8e1bcec3cd6b20ac783656355625b86319
Tx public key: e12e47d029f2d4b77658127755d08ea1d777077c42e60239689d7f38e1c13c8b
Timestamp: 1707531123 Timestamp [UCT]: 2024-02-10 02:12:03 Age [y:d:h:m:s]: 01:056:03:31:54
Block: 954170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301184 RingCT/type: yes/0
Extra: 01e12e47d029f2d4b77658127755d08ea1d777077c42e60239689d7f38e1c13c8b021100000002ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16255157f950122bccb074e3cfb095ce5f74077f91f0ee04e028c02a99b17dbc 0.600000000000 1413446 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": 954180, "vin": [ { "gen": { "height": 954170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16255157f950122bccb074e3cfb095ce5f74077f91f0ee04e028c02a99b17dbc" } } ], "extra": [ 1, 225, 46, 71, 208, 41, 242, 212, 183, 118, 88, 18, 119, 85, 208, 142, 161, 215, 119, 7, 124, 66, 230, 2, 57, 104, 157, 127, 56, 225, 193, 60, 139, 2, 17, 0, 0, 0, 2, 236, 87, 178, 52, 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