Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 525e74afffa83dce611d64edf9657158fdffc2befe854b4ed9e84ddac69f4a3f

Tx prefix hash: c88f9a83c04e127ce0e10a9f0445d10452f085ed27f6b1ac188d878f589e7b60
Tx public key: 4e78a12d6b1e7476cf87ce4b3281f474263e1e379b84e964fd77613af03157a7
Timestamp: 1674851687 Timestamp [UCT]: 2023-01-27 20:34:47 Age [y:d:h:m:s]: 02:069:15:17:49
Block: 684140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571395 RingCT/type: yes/0
Extra: 014e78a12d6b1e7476cf87ce4b3281f474263e1e379b84e964fd77613af03157a70211000000015029cbac000000000000000000

1 output(s) for total of 3.320168436000 dcy

stealth address amount amount idx
00: de2fd5c73e451c6f4bb6de626ab9414711aaeec923167f6207a5ef04ef8c961f 3.320168436000 1126353 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": 684150, "vin": [ { "gen": { "height": 684140 } } ], "vout": [ { "amount": 3320168436, "target": { "key": "de2fd5c73e451c6f4bb6de626ab9414711aaeec923167f6207a5ef04ef8c961f" } } ], "extra": [ 1, 78, 120, 161, 45, 107, 30, 116, 118, 207, 135, 206, 75, 50, 129, 244, 116, 38, 62, 30, 55, 155, 132, 233, 100, 253, 119, 97, 58, 240, 49, 87, 167, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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