Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31cafd801bddff05b3654001b31bd684fdc39a104c1b2c0425c848b4e66b45e5

Tx prefix hash: 69b6e9e7c0062f3ef589092782146d4c9d5d71ee70e32662012fa4e34c282425
Tx public key: d783f96d2a68c4d1bde0262ce696608db7efebd9334c51624c7b2ef3a964a05d
Timestamp: 1723308995 Timestamp [UCT]: 2024-08-10 16:56:35 Age [y:d:h:m:s]: 01:093:03:00:45
Block: 1084992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325027 RingCT/type: yes/0
Extra: 01d783f96d2a68c4d1bde0262ce696608db7efebd9334c51624c7b2ef3a964a05d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e92647211929d946e7096d9ed391dabbb36acd588971e7995bd1b18d57df11 0.600000000000 1559461 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": 1085002, "vin": [ { "gen": { "height": 1084992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e92647211929d946e7096d9ed391dabbb36acd588971e7995bd1b18d57df11" } } ], "extra": [ 1, 215, 131, 249, 109, 42, 104, 196, 209, 189, 224, 38, 44, 230, 150, 96, 141, 183, 239, 235, 217, 51, 76, 81, 98, 76, 123, 46, 243, 169, 100, 160, 93, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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