Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595c25a344aecb00fef8692e0c345934a18ab2475ea6ee5d75aa5f922aa19e0b

Tx prefix hash: f22f5c6211b6f22c44093a8ee477d92305f9abb3f5f2adac5099dfa43c88e378
Tx public key: c95b6e0c056ac0978b4534c95ca70160828e12a357e88e4d4fe9eea3530ee2dc
Timestamp: 1731383999 Timestamp [UCT]: 2024-11-12 03:59:59 Age [y:d:h:m:s]: 00:146:23:29:38
Block: 1151839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104865 RingCT/type: yes/0
Extra: 01c95b6e0c056ac0978b4534c95ca70160828e12a357e88e4d4fe9eea3530ee2dc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f68889018e303a83c348761509af80671c8d504ac162e99939e1e18eedbfb33 0.600000000000 1637422 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": 1151849, "vin": [ { "gen": { "height": 1151839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f68889018e303a83c348761509af80671c8d504ac162e99939e1e18eedbfb33" } } ], "extra": [ 1, 201, 91, 110, 12, 5, 106, 192, 151, 139, 69, 52, 201, 92, 167, 1, 96, 130, 142, 18, 163, 87, 232, 142, 77, 79, 233, 238, 163, 83, 14, 226, 220, 2, 17, 0, 0, 0, 1, 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