Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5687b9716c1ca83d9f237ad8b2fdba0a7330f321ea9c602da65bc3b80b619d7e

Tx prefix hash: d4a2e34952348d4480a144b6b409275159450bb6b6ec10dd325c80acda138046
Tx public key: c0eeb40e2936a30e5d051f99bedd8644cd94c88e8558bcabc7f46ac3d2298669
Timestamp: 1724047576 Timestamp [UCT]: 2024-08-19 06:06:16 Age [y:d:h:m:s]: 00:207:09:52:44
Block: 1091118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148112 RingCT/type: yes/0
Extra: 01c0eeb40e2936a30e5d051f99bedd8644cd94c88e8558bcabc7f46ac3d2298669021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fab37f243b6f0f4b59b9c7428bc65eb3ef5d061b133095ed49e5cf49d43ca58d 0.600000000000 1565747 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": 1091128, "vin": [ { "gen": { "height": 1091118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fab37f243b6f0f4b59b9c7428bc65eb3ef5d061b133095ed49e5cf49d43ca58d" } } ], "extra": [ 1, 192, 238, 180, 14, 41, 54, 163, 14, 93, 5, 31, 153, 190, 221, 134, 68, 205, 148, 200, 142, 133, 88, 188, 171, 199, 244, 106, 195, 210, 41, 134, 105, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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