Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 061e49b4379edc0d7994f378af26bbeedbb3e08dae30449fb4ccf851f27ef1da

Tx prefix hash: b5f2e5eaa2243340eae0aab1ff3e7e0740b0da22e40d9d550ceccc5f2ae72a59
Tx public key: fc9ecfa1a9241c744408ee23103cb9f392b6330aaf8ab73504240e9bb805cf1e
Timestamp: 1737804712 Timestamp [UCT]: 2025-01-25 11:31:52 Age [y:d:h:m:s]: 00:048:13:13:35
Block: 1204970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34517 RingCT/type: yes/0
Extra: 01fc9ecfa1a9241c744408ee23103cb9f392b6330aaf8ab73504240e9bb805cf1e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccf53905ee58a7e0fb5fcff97f33480a2a4a9b54d3045f67e872d3f8b2b7ffb6 0.600000000000 1691665 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": 1204980, "vin": [ { "gen": { "height": 1204970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccf53905ee58a7e0fb5fcff97f33480a2a4a9b54d3045f67e872d3f8b2b7ffb6" } } ], "extra": [ 1, 252, 158, 207, 161, 169, 36, 28, 116, 68, 8, 238, 35, 16, 60, 185, 243, 146, 182, 51, 10, 175, 138, 183, 53, 4, 36, 14, 155, 184, 5, 207, 30, 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