Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd1e4dadf96089655bb06236bad6ff1e078df9ac7b750c96827fea3d9a9e532

Tx prefix hash: cfcb3b5363e4b89ec4e4882751d462eedae4fb5c795acd33ad72549bee3a684c
Tx public key: c510d64dc49371f817dc593ae41abd5b56e29cd1f7aa0fe4aed9f91b037a8c89
Timestamp: 1715134814 Timestamp [UCT]: 2024-05-08 02:20:14 Age [y:d:h:m:s]: 00:363:04:22:01
Block: 1017220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259616 RingCT/type: yes/0
Extra: 01c510d64dc49371f817dc593ae41abd5b56e29cd1f7aa0fe4aed9f91b037a8c890211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aa98d855845954a99a8537bc68a215be3f06782245f1cc0c27cd2dfc18316e4 0.600000000000 1480989 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": 1017230, "vin": [ { "gen": { "height": 1017220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa98d855845954a99a8537bc68a215be3f06782245f1cc0c27cd2dfc18316e4" } } ], "extra": [ 1, 197, 16, 214, 77, 196, 147, 113, 248, 23, 220, 89, 58, 228, 26, 189, 91, 86, 226, 156, 209, 247, 170, 15, 228, 174, 217, 249, 27, 3, 122, 140, 137, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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