Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774b41315298d2cb11fb2349ded48d714ef5f5156638e6c3a692aa97f76e5e39

Tx prefix hash: 329ece3e59c538396460f829728f62bd8fb723fdb5e5a07c8f2df2e043aa59ee
Tx public key: bec47ad16cb6968dd9461fd6ae65d5c4cf6dc8ea2732cd57149330fdb3d9c0b1
Timestamp: 1756096940 Timestamp [UCT]: 2025-08-25 04:42:20 Age [y:d:h:m:s]: 00:157:04:08:15
Block: 1353896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112178 RingCT/type: yes/0
Extra: 01bec47ad16cb6968dd9461fd6ae65d5c4cf6dc8ea2732cd57149330fdb3d9c0b10211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac88fe6acc6d05593c432c76acc307cae224bfb698c70bcc70f6a9d3dfeb8a36 0.600000000000 1841875 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": 1353906, "vin": [ { "gen": { "height": 1353896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac88fe6acc6d05593c432c76acc307cae224bfb698c70bcc70f6a9d3dfeb8a36" } } ], "extra": [ 1, 190, 196, 122, 209, 108, 182, 150, 141, 217, 70, 31, 214, 174, 101, 213, 196, 207, 109, 200, 234, 39, 50, 205, 87, 20, 147, 48, 253, 179, 217, 192, 177, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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