Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a8240d3699e02f03304542a262e42bb871217a8fec17c55544662e8b5434304

Tx prefix hash: a598ac65fa1688dbbbb17b4f5dad00511d8f172b091e20c650c7440e5237ed29
Tx public key: afb97e62a1a83c3875dc84687ff7d1dcea50d2c326c73d6d96b759a07a282cbd
Timestamp: 1741431945 Timestamp [UCT]: 2025-03-08 11:05:45 Age [y:d:h:m:s]: 00:258:14:11:54
Block: 1234783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182553 RingCT/type: yes/0
Extra: 01afb97e62a1a83c3875dc84687ff7d1dcea50d2c326c73d6d96b759a07a282cbd0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b20c57972cd0b03c012da6d4e10c7c4c77f2b56beb8b12c2e755357cb3f62835 0.600000000000 1721718 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": 1234793, "vin": [ { "gen": { "height": 1234783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b20c57972cd0b03c012da6d4e10c7c4c77f2b56beb8b12c2e755357cb3f62835" } } ], "extra": [ 1, 175, 185, 126, 98, 161, 168, 60, 56, 117, 220, 132, 104, 127, 247, 209, 220, 234, 80, 210, 195, 38, 199, 61, 109, 150, 183, 89, 160, 122, 40, 44, 189, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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