Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f51556212cd5e3da0716e443aa285ae03c94233986693bb4aae3a6bdbdb680b

Tx prefix hash: 35665132c42b0af367a33cffee32a445c7b82c4e4b1941fcd7243b436d727898
Tx public key: 086ea96f91c13b6ffc2e1467f4ecccb6066ce64389eb7a2678b8dc36498ff0b5
Timestamp: 1703746081 Timestamp [UCT]: 2023-12-28 06:48:01 Age [y:d:h:m:s]: 01:342:19:43:06
Block: 922801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503897 RingCT/type: yes/0
Extra: 01086ea96f91c13b6ffc2e1467f4ecccb6066ce64389eb7a2678b8dc36498ff0b50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b941f44d9892f769076ceb60c04a3b61bc763bf010b2194b0cbd6ae235cc27d0 0.600000000000 1380505 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": 922811, "vin": [ { "gen": { "height": 922801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b941f44d9892f769076ceb60c04a3b61bc763bf010b2194b0cbd6ae235cc27d0" } } ], "extra": [ 1, 8, 110, 169, 111, 145, 193, 59, 111, 252, 46, 20, 103, 244, 236, 204, 182, 6, 108, 230, 67, 137, 235, 122, 38, 120, 184, 220, 54, 73, 143, 240, 181, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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