Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a0f479742938be877cb040644536f9e3c4a2b098362e7bcffbf2030858b41f4

Tx prefix hash: 49a560fa319d0e29794eb5706eaf8a59fa3114ef9e2806e2074e6ef6f1f13adc
Tx public key: 53c5eaf836edbef2f7c9cbb794d62f8b69931a666ccf4fb7fb87d69c578279e0
Timestamp: 1737300796 Timestamp [UCT]: 2025-01-19 15:33:16 Age [y:d:h:m:s]: 00:299:05:51:28
Block: 1200797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211419 RingCT/type: yes/0
Extra: 0153c5eaf836edbef2f7c9cbb794d62f8b69931a666ccf4fb7fb87d69c578279e0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc6238e3af49ee18010e34bb05fb51f953ae7129d8a5219047c83f232597047f 0.600000000000 1687444 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": 1200807, "vin": [ { "gen": { "height": 1200797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc6238e3af49ee18010e34bb05fb51f953ae7129d8a5219047c83f232597047f" } } ], "extra": [ 1, 83, 197, 234, 248, 54, 237, 190, 242, 247, 201, 203, 183, 148, 214, 47, 139, 105, 147, 26, 102, 108, 207, 79, 183, 251, 135, 214, 156, 87, 130, 121, 224, 2, 17, 0, 0, 0, 2, 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