Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91cbb11bfe16b64c5c1ccefec5f97ebdc6c1e31548d332b557eebb89441a7e9

Tx prefix hash: ac46392aee03fe59dff49b061d9f6d55ca9b3e8c0a0d1a8d5348f20d1e61ce21
Tx public key: 5799c4e6fcdceab1e658a7d26c4cbeaf199492dcaddb623ae93662a5e1de9dc2
Timestamp: 1754871576 Timestamp [UCT]: 2025-08-11 00:19:36 Age [y:d:h:m:s]: 00:009:19:00:07
Block: 1344452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6326 RingCT/type: yes/0
Extra: 015799c4e6fcdceab1e658a7d26c4cbeaf199492dcaddb623ae93662a5e1de9dc20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e2bfac7838a79353687f1e0adae9ca35756f70f86c6a5617fcae7133035bd9f 0.600000000000 1832335 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": 1344462, "vin": [ { "gen": { "height": 1344452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e2bfac7838a79353687f1e0adae9ca35756f70f86c6a5617fcae7133035bd9f" } } ], "extra": [ 1, 87, 153, 196, 230, 252, 220, 234, 177, 230, 88, 167, 210, 108, 76, 190, 175, 25, 148, 146, 220, 173, 219, 98, 58, 233, 54, 98, 165, 225, 222, 157, 194, 2, 17, 0, 0, 0, 1, 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