Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cb5d793fba56f5be6caec8154731e66f62fdef3cb857f7a233b04ebecc623b1

Tx prefix hash: 546c28e8a3d61d71bd1a9e3f3de31342bc153dced199c9bdd9ff12f0eca8371c
Tx public key: 00d0a8e57248b8354e258436b206802a44984751ffb824d3040001ae7989dcb1
Timestamp: 1728851425 Timestamp [UCT]: 2024-10-13 20:30:25 Age [y:d:h:m:s]: 00:193:02:36:17
Block: 1130938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137812 RingCT/type: yes/0
Extra: 0100d0a8e57248b8354e258436b206802a44984751ffb824d3040001ae7989dcb1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 613d4bab2da65caf2a8ff3a9b791a131396e7225477e29b77fa2d3b9eaadab3a 0.600000000000 1613819 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": 1130948, "vin": [ { "gen": { "height": 1130938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "613d4bab2da65caf2a8ff3a9b791a131396e7225477e29b77fa2d3b9eaadab3a" } } ], "extra": [ 1, 0, 208, 168, 229, 114, 72, 184, 53, 78, 37, 132, 54, 178, 6, 128, 42, 68, 152, 71, 81, 255, 184, 36, 211, 4, 0, 1, 174, 121, 137, 220, 177, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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