Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fab6f0dbf3c421ad76b1c223c43e3ff8ffceb74698b18d72446b9945459819f

Tx prefix hash: 8c2dc016bf199879c5c1f7499278ddc7481d7fa58a51dc4d35d213e9bf5e5367
Tx public key: c4b0df50e96857576584fa007c9a7ab40bb0c5d3bfac3dc678fd3b566426bf1b
Timestamp: 1736552641 Timestamp [UCT]: 2025-01-10 23:44:01 Age [y:d:h:m:s]: 00:011:08:56:25
Block: 1194637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8098 RingCT/type: yes/0
Extra: 01c4b0df50e96857576584fa007c9a7ab40bb0c5d3bfac3dc678fd3b566426bf1b021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6452c86f826b876bb10b7854cefd38620bc6df36d41bee4c320b189060833e84 0.600000000000 1681214 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": 1194647, "vin": [ { "gen": { "height": 1194637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6452c86f826b876bb10b7854cefd38620bc6df36d41bee4c320b189060833e84" } } ], "extra": [ 1, 196, 176, 223, 80, 233, 104, 87, 87, 101, 132, 250, 0, 124, 154, 122, 180, 11, 176, 197, 211, 191, 172, 61, 198, 120, 253, 59, 86, 100, 38, 191, 27, 2, 17, 0, 0, 0, 7, 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