Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51302d7d4654c9f89932235b62f2a8606d96aa3cff7ea30c553f18be3239cbca

Tx prefix hash: 67d71b93dbedff7c623d448d008197a022a7c8e11536eb8d73d9879e1002d9bb
Tx public key: d8f980fb1d54fac7f4cfc4f2857f225865edc02414755b9e82e74d10dec1e492
Timestamp: 1704647806 Timestamp [UCT]: 2024-01-07 17:16:46 Age [y:d:h:m:s]: 01:310:03:48:27
Block: 930265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480499 RingCT/type: yes/0
Extra: 01d8f980fb1d54fac7f4cfc4f2857f225865edc02414755b9e82e74d10dec1e4920211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39be36ce8b723bda579357682ef7c000f91f862f8c6d0232406da827ae4a464 0.600000000000 1388147 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": 930275, "vin": [ { "gen": { "height": 930265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39be36ce8b723bda579357682ef7c000f91f862f8c6d0232406da827ae4a464" } } ], "extra": [ 1, 216, 249, 128, 251, 29, 84, 250, 199, 244, 207, 196, 242, 133, 127, 34, 88, 101, 237, 192, 36, 20, 117, 91, 158, 130, 231, 77, 16, 222, 193, 228, 146, 2, 17, 0, 0, 0, 17, 122, 156, 244, 199, 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