Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c1102d29b7b4424b1f7e22221071304f241ebd7e1957689a5ba53ba94ea5a6

Tx prefix hash: 747acc666a881c4198e8c258b99ee9386f0b5f75f91b63799fe4888a37a8565f
Tx public key: 3bbedc7cc389adc9d4ee4f68b27c1b9f13c8fbad8b3d38100518515563484727
Timestamp: 1722175826 Timestamp [UCT]: 2024-07-28 14:10:26 Age [y:d:h:m:s]: 00:250:01:38:58
Block: 1075589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178640 RingCT/type: yes/0
Extra: 013bbedc7cc389adc9d4ee4f68b27c1b9f13c8fbad8b3d3810051851556348472702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 092fa43d91e0ed23d5041c2d0e8d4fd5d4fbbff40fb6aed00fa7927ab3ca15a1 0.600000000000 1548118 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": 1075599, "vin": [ { "gen": { "height": 1075589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "092fa43d91e0ed23d5041c2d0e8d4fd5d4fbbff40fb6aed00fa7927ab3ca15a1" } } ], "extra": [ 1, 59, 190, 220, 124, 195, 137, 173, 201, 212, 238, 79, 104, 178, 124, 27, 159, 19, 200, 251, 173, 139, 61, 56, 16, 5, 24, 81, 85, 99, 72, 71, 39, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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