Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b87c226cae835f78f597f48ec8d207be2ba32cd79563be195cbd4992aba2d0

Tx prefix hash: a04eb08acf24fac150ee2e1be137cee90fef678992d0d7a18571f12f0918f2d3
Tx public key: 2fe809cfb7298d777f2d9498a7d9bfb6e67baf93beac33134e0b793869ee9095
Timestamp: 1698406847 Timestamp [UCT]: 2023-10-27 11:40:47 Age [y:d:h:m:s]: 01:087:20:01:04
Block: 878757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323960 RingCT/type: yes/0
Extra: 012fe809cfb7298d777f2d9498a7d9bfb6e67baf93beac33134e0b793869ee9095021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.752165283000 dcy

stealth address amount amount idx
00: a4c385cdf1104fab97702df24bf063fbfa37237a8f1fb4e95f855dd28003b7f1 0.752165283000 1334231 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": 878767, "vin": [ { "gen": { "height": 878757 } } ], "vout": [ { "amount": 752165283, "target": { "key": "a4c385cdf1104fab97702df24bf063fbfa37237a8f1fb4e95f855dd28003b7f1" } } ], "extra": [ 1, 47, 232, 9, 207, 183, 41, 141, 119, 127, 45, 148, 152, 167, 217, 191, 182, 230, 123, 175, 147, 190, 172, 51, 19, 78, 11, 121, 56, 105, 238, 144, 149, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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