Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb83944498c2478cd1d2e7b22ed6ee8a1524755571263a2d9b8cd0f6b6aa5ac2

Tx prefix hash: 66a93adf49cc5e65d2b4e3fc496c0ee2e8a6c07c1355964bae075df4c8052f28
Tx public key: eef4e6010a98e26c2c7ba38a73dc73753dc059a97af1008a7f4a62195d36cc79
Timestamp: 1764699999 Timestamp [UCT]: 2025-12-02 18:26:39 Age [y:d:h:m:s]: 00:037:11:33:23
Block: 1425011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26839 RingCT/type: yes/0
Extra: 01eef4e6010a98e26c2c7ba38a73dc73753dc059a97af1008a7f4a62195d36cc79021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a87e4f2fc613a7fa425e99bba129cf546ecd07801fa4d2e7e642f924a48fd0a6 0.600000000000 1913644 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": 1425021, "vin": [ { "gen": { "height": 1425011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a87e4f2fc613a7fa425e99bba129cf546ecd07801fa4d2e7e642f924a48fd0a6" } } ], "extra": [ 1, 238, 244, 230, 1, 10, 152, 226, 108, 44, 123, 163, 138, 115, 220, 115, 117, 61, 192, 89, 169, 122, 241, 0, 138, 127, 74, 98, 25, 93, 54, 204, 121, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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