Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9600a26c49a5015c9364e58e28e754e2f99bba38635a22b18af120e7ae5d10fc

Tx prefix hash: a52ee8061bd61673b53f22825412ee0abf9cf174f7d313c8c8f61de79f84b386
Tx public key: be7d7f324a48f2edececfe02c3c100fb1fb99dd5176d953e784a518d2f16cbcb
Timestamp: 1740905881 Timestamp [UCT]: 2025-03-02 08:58:01 Age [y:d:h:m:s]: 00:263:19:04:06
Block: 1230414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186276 RingCT/type: yes/0
Extra: 01be7d7f324a48f2edececfe02c3c100fb1fb99dd5176d953e784a518d2f16cbcb02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df11f77a5bcd06b6522951bbe139d86ac179295cf14a478d1ecfb3cfa9551d9b 0.600000000000 1717311 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": 1230424, "vin": [ { "gen": { "height": 1230414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df11f77a5bcd06b6522951bbe139d86ac179295cf14a478d1ecfb3cfa9551d9b" } } ], "extra": [ 1, 190, 125, 127, 50, 74, 72, 242, 237, 236, 236, 254, 2, 195, 193, 0, 251, 31, 185, 157, 213, 23, 109, 149, 62, 120, 74, 81, 141, 47, 22, 203, 203, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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