Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66ff96b9a212538901e3934122595af3801e20a54ee49d19bd1ccfaf3e85a201

Tx prefix hash: dd934d354b1501756bcdc7f7c9b623c81a1c0a5e190411f4c2188f2e6339fbd4
Tx public key: 2cd48f688d1ae93523a86731c270ff80b194e94a7a4dc729049e74b1702fbfa3
Timestamp: 1639150641 Timestamp [UCT]: 2021-12-10 15:37:21 Age [y:d:h:m:s]: 03:029:08:17:05
Block: 392584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799917 RingCT/type: yes/0
Extra: 012cd48f688d1ae93523a86731c270ff80b194e94a7a4dc729049e74b1702fbfa3021100000001a272b9cb000000000000000000

1 output(s) for total of 30.704823192000 dcy

stealth address amount amount idx
00: 57acce654e28918178458fa1d57ae3f06253abc70e6e46c59da9a2cbc9efb5a8 30.704823192000 789511 of 0

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": 392594, "vin": [ { "gen": { "height": 392584 } } ], "vout": [ { "amount": 30704823192, "target": { "key": "57acce654e28918178458fa1d57ae3f06253abc70e6e46c59da9a2cbc9efb5a8" } } ], "extra": [ 1, 44, 212, 143, 104, 141, 26, 233, 53, 35, 168, 103, 49, 194, 112, 255, 128, 177, 148, 233, 74, 122, 77, 199, 41, 4, 158, 116, 177, 112, 47, 191, 163, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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