Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c547757d2e12d2d1c70015aacd42436593ef159015d089d09b5b9bb291c9000a

Tx prefix hash: 697a352f2a9210fa1ac25904e5029b629e1e02ab53d1971019b92362605834f6
Tx public key: 726a584e63e0de27ba5138d0ea053b468414a0956aaa5e3895d0a20feed8e2ae
Timestamp: 1727558911 Timestamp [UCT]: 2024-09-28 21:28:31 Age [y:d:h:m:s]: 00:228:06:50:10
Block: 1120227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162981 RingCT/type: yes/0
Extra: 01726a584e63e0de27ba5138d0ea053b468414a0956aaa5e3895d0a20feed8e2ae021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8302898fef16f9e0c63e6be71720d768e24cf43efa9e5bfa7bb3b0f27b97067 0.600000000000 1602068 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": 1120237, "vin": [ { "gen": { "height": 1120227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8302898fef16f9e0c63e6be71720d768e24cf43efa9e5bfa7bb3b0f27b97067" } } ], "extra": [ 1, 114, 106, 88, 78, 99, 224, 222, 39, 186, 81, 56, 208, 234, 5, 59, 70, 132, 20, 160, 149, 106, 170, 94, 56, 149, 208, 162, 15, 238, 216, 226, 174, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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