Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a655c0255f19412a834afd81548f73d96166e3aa4fd23fd679157259120851e8

Tx prefix hash: 590d0f894f98dcf2860567d6ae75cf04ee00133bf7d65bdb0eedaa5f71012933
Tx public key: f5e6fb7f71c83b305fa0723e2121b4e9dbd92ad2f3accb6be807dbc5512c90c0
Timestamp: 1736461165 Timestamp [UCT]: 2025-01-09 22:19:25 Age [y:d:h:m:s]: 00:082:10:47:40
Block: 1193889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58694 RingCT/type: yes/0
Extra: 01f5e6fb7f71c83b305fa0723e2121b4e9dbd92ad2f3accb6be807dbc5512c90c00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e505cb45abf86ffaf2605f4cc35ebcdb0f215126705d850e5334086c5ad7265 0.600000000000 1680454 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": 1193899, "vin": [ { "gen": { "height": 1193889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e505cb45abf86ffaf2605f4cc35ebcdb0f215126705d850e5334086c5ad7265" } } ], "extra": [ 1, 245, 230, 251, 127, 113, 200, 59, 48, 95, 160, 114, 62, 33, 33, 180, 233, 219, 217, 42, 210, 243, 172, 203, 107, 232, 7, 219, 197, 81, 44, 144, 192, 2, 17, 0, 0, 0, 8, 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