Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f848e0e170e3fed86fa5506c79eb2f26115fd96cb2684e5870abd27c3ae96b01

Tx prefix hash: 4bc085763ef83a86fe082eb7469774980308aa0fb8055a7d0ee10db4477c9cf0
Tx public key: 0e0770e43bf9e115d518f9b1c64eabfa9768d210100f360c4ad0763bea6b6b1b
Timestamp: 1759913779 Timestamp [UCT]: 2025-10-08 08:56:19 Age [y:d:h:m:s]: 00:116:03:53:02
Block: 1385332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83002 RingCT/type: yes/0
Extra: 010e0770e43bf9e115d518f9b1c64eabfa9768d210100f360c4ad0763bea6b6b1b021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bed43a292a109cc21c3744c9f3a1f194fd3458f76e2b291e3c56c7218a8e2a05 0.600000000000 1873495 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": 1385342, "vin": [ { "gen": { "height": 1385332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bed43a292a109cc21c3744c9f3a1f194fd3458f76e2b291e3c56c7218a8e2a05" } } ], "extra": [ 1, 14, 7, 112, 228, 59, 249, 225, 21, 213, 24, 249, 177, 198, 78, 171, 250, 151, 104, 210, 16, 16, 15, 54, 12, 74, 208, 118, 59, 234, 107, 107, 27, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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