Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf35a204430b6f54357d18708e3f6d8b6444cb7ccbfe1561a5c8c853da2f708

Tx prefix hash: 89427a4adddaa6d4aa3ba151dfd2616153d1acbf17af73b341dae67a844ccd51
Tx public key: ce91e9afc5c5cc2b110c2442d546ff348f6be20726f1ded9cbed88ae71a9fc89
Timestamp: 1737015010 Timestamp [UCT]: 2025-01-16 08:10:10 Age [y:d:h:m:s]: 00:153:08:21:17
Block: 1198464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109306 RingCT/type: yes/0
Extra: 01ce91e9afc5c5cc2b110c2442d546ff348f6be20726f1ded9cbed88ae71a9fc89021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afcf5b322d7ddd68b8d35a6651bca43324f6c879912d65666bc183c6b206fa34 0.600000000000 1685089 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": 1198474, "vin": [ { "gen": { "height": 1198464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afcf5b322d7ddd68b8d35a6651bca43324f6c879912d65666bc183c6b206fa34" } } ], "extra": [ 1, 206, 145, 233, 175, 197, 197, 204, 43, 17, 12, 36, 66, 213, 70, 255, 52, 143, 107, 226, 7, 38, 241, 222, 217, 203, 237, 136, 174, 113, 169, 252, 137, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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