Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357c5485fd229a9e722569cabf775cae763d685c042129be18bc9339a210d114

Tx prefix hash: a3e46200d46f346078690f399ad80e06437cd98f3a7be1993012e34519e40fd4
Tx public key: fec9e5ec53092b545fec6af2d60df647031c417a4c1b3e01a40b0f0ac15c432f
Timestamp: 1727887817 Timestamp [UCT]: 2024-10-02 16:50:17 Age [y:d:h:m:s]: 01:038:19:31:20
Block: 1122958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286119 RingCT/type: yes/0
Extra: 01fec9e5ec53092b545fec6af2d60df647031c417a4c1b3e01a40b0f0ac15c432f02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a9f537c95ad1f413f93a8a52f088d27d32c383d45781db779e42c8c894c9192 0.600000000000 1605491 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": 1122968, "vin": [ { "gen": { "height": 1122958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a9f537c95ad1f413f93a8a52f088d27d32c383d45781db779e42c8c894c9192" } } ], "extra": [ 1, 254, 201, 229, 236, 83, 9, 43, 84, 95, 236, 106, 242, 214, 13, 246, 71, 3, 28, 65, 122, 76, 27, 62, 1, 164, 11, 15, 10, 193, 92, 67, 47, 2, 17, 0, 0, 0, 8, 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