Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d6d7835e6da475590691c562f08cf6c0ee5e0e94d5540d46e6e698bf018cbb6

Tx prefix hash: 8d07e00ef7787231d039019a58d13b4f0122bdd89431a5ede3bc45cf544ea67a
Tx public key: d55f1eae70fe95368fa8fab5be0a1beece0af2b8575aa8b0a73c776978c4192c
Timestamp: 1701343254 Timestamp [UCT]: 2023-11-30 11:20:54 Age [y:d:h:m:s]: 01:134:19:45:26
Block: 902861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357538 RingCT/type: yes/0
Extra: 01d55f1eae70fe95368fa8fab5be0a1beece0af2b8575aa8b0a73c776978c4192c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.625816041000 dcy

stealth address amount amount idx
00: af7a4e3c51e4783570546dc1aa8ea0236f1c1a03d1448aba7a5d0cfb0add8237 0.625816041000 1359524 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": 902871, "vin": [ { "gen": { "height": 902861 } } ], "vout": [ { "amount": 625816041, "target": { "key": "af7a4e3c51e4783570546dc1aa8ea0236f1c1a03d1448aba7a5d0cfb0add8237" } } ], "extra": [ 1, 213, 95, 30, 174, 112, 254, 149, 54, 143, 168, 250, 181, 190, 10, 27, 238, 206, 10, 242, 184, 87, 90, 168, 176, 167, 60, 119, 105, 120, 196, 25, 44, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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