Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e756b8c1bf2f331f11368ccd400660f87c0e48f9207a10bb201716a05f3bfcbe

Tx prefix hash: c43b78ac4df707c25b5af20daceda8a77dd09a7d7a7137c95504f07920354736
Tx public key: 590e1112b084670e2824f96d843739847d44d54c5d21fe34b09ae3222db3df2e
Timestamp: 1731613851 Timestamp [UCT]: 2024-11-14 19:50:51 Age [y:d:h:m:s]: 00:190:12:00:46
Block: 1153756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136002 RingCT/type: yes/0
Extra: 01590e1112b084670e2824f96d843739847d44d54c5d21fe34b09ae3222db3df2e02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52bc38e1d4c51bd0b18bf6b7fba758a227d238d6e9d95a44de7dec54c495252 0.600000000000 1639367 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": 1153766, "vin": [ { "gen": { "height": 1153756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52bc38e1d4c51bd0b18bf6b7fba758a227d238d6e9d95a44de7dec54c495252" } } ], "extra": [ 1, 89, 14, 17, 18, 176, 132, 103, 14, 40, 36, 249, 109, 132, 55, 57, 132, 125, 68, 213, 76, 93, 33, 254, 52, 176, 154, 227, 34, 45, 179, 223, 46, 2, 17, 0, 0, 0, 11, 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