Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a099bd8b49765f0e5cc375b3b0b3e52f7a39c18acb80e97dbd16a83a7179286

Tx prefix hash: e2ddf12750447dfdfb84106c7ef059b6a128006cae9f1eb264c621a120369ba1
Tx public key: 62c5a5d4a56504e43561acfe78544596b0751c1181b96556a41fc44b7aa4ca6e
Timestamp: 1747213733 Timestamp [UCT]: 2025-05-14 09:08:53 Age [y:d:h:m:s]: 00:146:22:25:57
Block: 1282645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102656 RingCT/type: yes/0
Extra: 0162c5a5d4a56504e43561acfe78544596b0751c1181b96556a41fc44b7aa4ca6e0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21ec5adc230d299e8e10b8364f5cefbe5a61157d2b9c7dc0459a11ab3be3ccd 0.600000000000 1770052 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": 1282655, "vin": [ { "gen": { "height": 1282645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21ec5adc230d299e8e10b8364f5cefbe5a61157d2b9c7dc0459a11ab3be3ccd" } } ], "extra": [ 1, 98, 197, 165, 212, 165, 101, 4, 228, 53, 97, 172, 254, 120, 84, 69, 150, 176, 117, 28, 17, 129, 185, 101, 86, 164, 31, 196, 75, 122, 164, 202, 110, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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