Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f64f80c48a8ac83bb90fa227a92bc308ca9fe741647521c86b4dd22c7ef93d

Tx prefix hash: fa0b05f6f3b37f6546a5095e7a75af63d6f8c62b6b38314c8fd6f1067b927ac8
Tx public key: 666c8333dac2a7c885fe12d251e2654b5345e673f9eafd6a81c652aa18999da3
Timestamp: 1734368759 Timestamp [UCT]: 2024-12-16 17:05:59 Age [y:d:h:m:s]: 00:024:18:57:42
Block: 1176587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17711 RingCT/type: yes/0
Extra: 01666c8333dac2a7c885fe12d251e2654b5345e673f9eafd6a81c652aa18999da3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb362dd6899569c3bf9343e8a6309cfbec9dce15e2d0486205285b2fc5e45718 0.600000000000 1662940 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": 1176597, "vin": [ { "gen": { "height": 1176587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb362dd6899569c3bf9343e8a6309cfbec9dce15e2d0486205285b2fc5e45718" } } ], "extra": [ 1, 102, 108, 131, 51, 218, 194, 167, 200, 133, 254, 18, 210, 81, 226, 101, 75, 83, 69, 230, 115, 249, 234, 253, 106, 129, 198, 82, 170, 24, 153, 157, 163, 2, 17, 0, 0, 0, 3, 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