Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a387bd2f0a8b2177b90f57d8393b44a4719d85a35a444b243624fd206e8c9112

Tx prefix hash: ab75b80454ff4ee47bed4843b42e4007adc1966d2ca2dbf7b76c845f97956b58
Tx public key: 1f40422ed41b8863dcd4a81d025aadb207c76d26d9447e2d789b052df2d380ec
Timestamp: 1726702351 Timestamp [UCT]: 2024-09-18 23:32:31 Age [y:d:h:m:s]: 00:125:20:17:41
Block: 1113121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89943 RingCT/type: yes/0
Extra: 011f40422ed41b8863dcd4a81d025aadb207c76d26d9447e2d789b052df2d380ec02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80d2fa91213e91696e222b6718a16c02cedb8ae8111ac8fb10233477d843c085 0.600000000000 1592680 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": 1113131, "vin": [ { "gen": { "height": 1113121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80d2fa91213e91696e222b6718a16c02cedb8ae8111ac8fb10233477d843c085" } } ], "extra": [ 1, 31, 64, 66, 46, 212, 27, 136, 99, 220, 212, 168, 29, 2, 90, 173, 178, 7, 199, 109, 38, 217, 68, 126, 45, 120, 155, 5, 45, 242, 211, 128, 236, 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