Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f549f6eb9b483b4c16ef6c2ccad07e0c0ae316c05ffe5b6c117b70928451b4

Tx prefix hash: b306843a7861b6afe4a2a1268dc2d8d86287226eb599617b395b103d78c47796
Tx public key: b3863c5af3594766ccaa180a28c7ad90491cbf70ddcaa6480195a4ca924f3e4d
Timestamp: 1687413002 Timestamp [UCT]: 2023-06-22 05:50:02 Age [y:d:h:m:s]: 01:211:01:09:14
Block: 787649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412223 RingCT/type: yes/0
Extra: 01b3863c5af3594766ccaa180a28c7ad90491cbf70ddcaa6480195a4ca924f3e4d0211000000024b8f5122000000000000000000

1 output(s) for total of 1.507273426000 dcy

stealth address amount amount idx
00: 22eb1e3536718e947a58a31ad8e70ce57614b072d64e2e4a163dc499d9c47c16 1.507273426000 1237718 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": 787659, "vin": [ { "gen": { "height": 787649 } } ], "vout": [ { "amount": 1507273426, "target": { "key": "22eb1e3536718e947a58a31ad8e70ce57614b072d64e2e4a163dc499d9c47c16" } } ], "extra": [ 1, 179, 134, 60, 90, 243, 89, 71, 102, 204, 170, 24, 10, 40, 199, 173, 144, 73, 28, 191, 112, 221, 202, 166, 72, 1, 149, 164, 202, 146, 79, 62, 77, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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