Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c2e5712117da0fd190a7b092c9ec1261ca7c65c5694b6e19162af96fcb614f

Tx prefix hash: ccb188ddf821fc7e294673e5140ffaff6012bbe3f22946fc1a89a58c0e451177
Tx public key: e520886689e5596340343f064a9b9ec3cb88e2eb62fa66bb9892f1d33a91009d
Timestamp: 1695813802 Timestamp [UCT]: 2023-09-27 11:23:22 Age [y:d:h:m:s]: 01:153:19:08:27
Block: 857242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370939 RingCT/type: yes/0
Extra: 01e520886689e5596340343f064a9b9ec3cb88e2eb62fa66bb9892f1d33a91009d02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.886342230000 dcy

stealth address amount amount idx
00: 19cd0a1e97baf9d96bf7d7143b60ae59bd32d0c2b2508fb696229849cace3ef1 0.886342230000 1311354 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": 857252, "vin": [ { "gen": { "height": 857242 } } ], "vout": [ { "amount": 886342230, "target": { "key": "19cd0a1e97baf9d96bf7d7143b60ae59bd32d0c2b2508fb696229849cace3ef1" } } ], "extra": [ 1, 229, 32, 136, 102, 137, 229, 89, 99, 64, 52, 63, 6, 74, 155, 158, 195, 203, 136, 226, 235, 98, 250, 102, 187, 152, 146, 241, 211, 58, 145, 0, 157, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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