Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3421f03dd1b079eaefedfc45bd764f9a6080bc4f01af461faca447ae0f5374d3

Tx prefix hash: d39a76e88be9e4e4c61ae507e81e4ceabe6d041cc40307d5cf820aa03f814857
Tx public key: 9d4a5ea2230c86695bab45124cf652a1c4f977bc57b8912196835e77f4e0e425
Timestamp: 1577192625 Timestamp [UCT]: 2019-12-24 13:03:45 Age [y:d:h:m:s]: 05:130:00:05:22
Block: 30719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242733 RingCT/type: yes/0
Extra: 019d4a5ea2230c86695bab45124cf652a1c4f977bc57b8912196835e77f4e0e4250211000000a178873133000000000000000000

1 output(s) for total of 485.529991998000 dcy

stealth address amount amount idx
00: 54eb600f60bdd4afa68036a82959fcd328dc9bff030d089af1586d182de14307 485.529991998000 50715 of 0

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": 30729, "vin": [ { "gen": { "height": 30719 } } ], "vout": [ { "amount": 485529991998, "target": { "key": "54eb600f60bdd4afa68036a82959fcd328dc9bff030d089af1586d182de14307" } } ], "extra": [ 1, 157, 74, 94, 162, 35, 12, 134, 105, 91, 171, 69, 18, 76, 246, 82, 161, 196, 249, 119, 188, 87, 184, 145, 33, 150, 131, 94, 119, 244, 224, 228, 37, 2, 17, 0, 0, 0, 161, 120, 135, 49, 51, 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