Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca74f5720f16a12bc6d79e711d1842d9ad23175816f12a04981930a59443dd7b

Tx prefix hash: 6331db49d5ad849952ba5e201be63482035e8bab6ec853bca4dfc284e9ff0003
Tx public key: 908d7c57348e11e8afcb7813065ad9d3a3c69f0e16167ddc4f6b2029aaea9063
Timestamp: 1711445735 Timestamp [UCT]: 2024-03-26 09:35:35 Age [y:d:h:m:s]: 01:270:13:26:02
Block: 986660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452087 RingCT/type: yes/0
Extra: 01908d7c57348e11e8afcb7813065ad9d3a3c69f0e16167ddc4f6b2029aaea906302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f878241e57ca3a3fa87545be6c37852eb2e1c0d4ad438563faccc77f52c3f185 0.600000000000 1446893 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": 986670, "vin": [ { "gen": { "height": 986660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f878241e57ca3a3fa87545be6c37852eb2e1c0d4ad438563faccc77f52c3f185" } } ], "extra": [ 1, 144, 141, 124, 87, 52, 142, 17, 232, 175, 203, 120, 19, 6, 90, 217, 211, 163, 198, 159, 14, 22, 22, 125, 220, 79, 107, 32, 41, 170, 234, 144, 99, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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