Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43934db760e9667ef2a392ebc935d0aefab9f7cfb19988bf5eae328698a1ab04

Tx prefix hash: fd4a4d68930be24690867ae59b8b5d61b4d98f8f975704957fc32f0c49e3e143
Tx public key: b9ef8814da548f542441e5a3e3c9dc3f6eefe7f7892995f50b6c6b805e35c9ce
Timestamp: 1574712803 Timestamp [UCT]: 2019-11-25 20:13:23 Age [y:d:h:m:s]: 05:035:00:19:19
Block: 17391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167854 RingCT/type: yes/0
Extra: 01b9ef8814da548f542441e5a3e3c9dc3f6eefe7f7892995f50b6c6b805e35c9ce021100000001f95225a5000000000000000000

1 output(s) for total of 537.498526861000 dcy

stealth address amount amount idx
00: 2868a8ca749d13bcb3e1efb2fe9c1bd9ff9b2e3fd868cd720031ad9bd8c3a457 537.498526861000 25231 of 0

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": 17401, "vin": [ { "gen": { "height": 17391 } } ], "vout": [ { "amount": 537498526861, "target": { "key": "2868a8ca749d13bcb3e1efb2fe9c1bd9ff9b2e3fd868cd720031ad9bd8c3a457" } } ], "extra": [ 1, 185, 239, 136, 20, 218, 84, 143, 84, 36, 65, 229, 163, 227, 201, 220, 63, 110, 239, 231, 247, 137, 41, 149, 245, 11, 108, 107, 128, 94, 53, 201, 206, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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