Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f85e1c217af04310e387704b84effe74a2f9d39b9e2eb8acfce38f17f1bec6af

Tx prefix hash: c3bc56481865991e48e283f89342fae6a0974b6a8720fe8402f3bc33e2ae0c6e
Tx public key: 56c60dce034b941157a6a89604416259df15e584df60066e35a8eb204077dc20
Timestamp: 1722167958 Timestamp [UCT]: 2024-07-28 11:59:18 Age [y:d:h:m:s]: 00:183:04:58:59
Block: 1075523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130842 RingCT/type: yes/0
Extra: 0156c60dce034b941157a6a89604416259df15e584df60066e35a8eb204077dc20021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc4ca1e82dde6b9be414548ebd8e7af0487e0c0f7320b47a88fedadc33518009 0.600000000000 1548052 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": 1075533, "vin": [ { "gen": { "height": 1075523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc4ca1e82dde6b9be414548ebd8e7af0487e0c0f7320b47a88fedadc33518009" } } ], "extra": [ 1, 86, 198, 13, 206, 3, 75, 148, 17, 87, 166, 168, 150, 4, 65, 98, 89, 223, 21, 229, 132, 223, 96, 6, 110, 53, 168, 235, 32, 64, 119, 220, 32, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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