Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8663cfa99e8adaf43e4e8c11266a9e31463f4cfbdeb6f2b02fbe12b57a4b32e8

Tx prefix hash: 027f1d9ca3f5dc19fa213bc259a0e84f99fa16bf80873fbbe1af378d2c7beeaa
Tx public key: 262f3f344737a4d663e51b9afcb7f3cd38403117c17acff185321f36cd68f4a4
Timestamp: 1707657407 Timestamp [UCT]: 2024-02-11 13:16:47 Age [y:d:h:m:s]: 01:035:14:26:58
Block: 955215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286498 RingCT/type: yes/0
Extra: 01262f3f344737a4d663e51b9afcb7f3cd38403117c17acff185321f36cd68f4a40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d379b048fcf50da30c197f6ca9355c34be220136e0f33bdd653c9fed9ae8792 0.600000000000 1414501 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": 955225, "vin": [ { "gen": { "height": 955215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d379b048fcf50da30c197f6ca9355c34be220136e0f33bdd653c9fed9ae8792" } } ], "extra": [ 1, 38, 47, 63, 52, 71, 55, 164, 214, 99, 229, 27, 154, 252, 183, 243, 205, 56, 64, 49, 23, 193, 122, 207, 241, 133, 50, 31, 54, 205, 104, 244, 164, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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