Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4caf41b0d3c6908dd1a4de2bf7a590b3e1debb858743f64e762ac5430005d99

Tx prefix hash: 010e51bd7bdd12287e11cf572b94ce3cf44e2bf54ac3e7dcf91430b25e42bdf2
Tx public key: 107725aab7d9bd37a1a9d08f7084ef969f1b59461fce286d05c2d14d59d7dca3
Timestamp: 1705525011 Timestamp [UCT]: 2024-01-17 20:56:51 Age [y:d:h:m:s]: 01:301:06:58:52
Block: 937524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474168 RingCT/type: yes/0
Extra: 01107725aab7d9bd37a1a9d08f7084ef969f1b59461fce286d05c2d14d59d7dca30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22a81a2f50ff83f7c3b8032f64a8464aed0a63770033cd34571aab08cc7ecb97 0.600000000000 1395580 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": 937534, "vin": [ { "gen": { "height": 937524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22a81a2f50ff83f7c3b8032f64a8464aed0a63770033cd34571aab08cc7ecb97" } } ], "extra": [ 1, 16, 119, 37, 170, 183, 217, 189, 55, 161, 169, 208, 143, 112, 132, 239, 150, 159, 27, 89, 70, 31, 206, 40, 109, 5, 194, 209, 77, 89, 215, 220, 163, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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