Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5c885cb7278731a62faa27b19fbdd392b9e59b5a21f9732799ddfed0e243ade

Tx prefix hash: 41a15dbf1f980d5a09d5913a2fac96e172e3dac069e22d87446f040313056803
Tx public key: 8a081032ab644c37a7c90455caa270729d50b3ad0b3b73c3dd62cabe9f3c0104
Timestamp: 1710433965 Timestamp [UCT]: 2024-03-14 16:32:45 Age [y:d:h:m:s]: 01:085:11:58:48
Block: 978273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322116 RingCT/type: yes/0
Extra: 018a081032ab644c37a7c90455caa270729d50b3ad0b3b73c3dd62cabe9f3c010402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1fe24bbc27f8abcc59fd56aa128e0b5d494de7a1e38fe902bef954362db3d6 0.600000000000 1438296 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": 978283, "vin": [ { "gen": { "height": 978273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1fe24bbc27f8abcc59fd56aa128e0b5d494de7a1e38fe902bef954362db3d6" } } ], "extra": [ 1, 138, 8, 16, 50, 171, 100, 76, 55, 167, 201, 4, 85, 202, 162, 112, 114, 157, 80, 179, 173, 11, 59, 115, 195, 221, 98, 202, 190, 159, 60, 1, 4, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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