Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6356be1617dde564609901339f1cbda4df84376f0145bc76b0e599fc4c8c9d42

Tx prefix hash: 943f5dafa462ad93b4b1a9679e2386f6f899198501f98e43ce32ebe14a9d1ee3
Tx public key: f41d76e99b8379ccd8c086a940b7b32fec663fd8d6fef9515713a754e465599c
Timestamp: 1727519958 Timestamp [UCT]: 2024-09-28 10:39:18 Age [y:d:h:m:s]: 00:179:02:01:02
Block: 1119901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127779 RingCT/type: yes/0
Extra: 01f41d76e99b8379ccd8c086a940b7b32fec663fd8d6fef9515713a754e465599c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c026b39d22f3c9dc4b5781d7a8fe9f5005909063adf1e77b69337ab25d5631cc 0.600000000000 1601628 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": 1119911, "vin": [ { "gen": { "height": 1119901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c026b39d22f3c9dc4b5781d7a8fe9f5005909063adf1e77b69337ab25d5631cc" } } ], "extra": [ 1, 244, 29, 118, 233, 155, 131, 121, 204, 216, 192, 134, 169, 64, 183, 179, 47, 236, 102, 63, 216, 214, 254, 249, 81, 87, 19, 167, 84, 228, 101, 89, 156, 2, 17, 0, 0, 0, 1, 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