Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a4e215f027876fb00c1c8c1ad1efb6ea5b5054c8ba06630b372a71095d4592

Tx prefix hash: 38bf73092ed444409ec808846c741598d596fcf6b009d7c231edab81362d7653
Tx public key: a2c8132106462c790d4dbca884e5a22d052ce6fc0cd4ee959e30490e0f84a37a
Timestamp: 1736060785 Timestamp [UCT]: 2025-01-05 07:06:25 Age [y:d:h:m:s]: 00:094:21:13:14
Block: 1190582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67594 RingCT/type: yes/0
Extra: 01a2c8132106462c790d4dbca884e5a22d052ce6fc0cd4ee959e30490e0f84a37a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d937bda7675e8392c1958cb1f6b25ad3d52ba0960f1ab4b1423bc4b9a9a558f4 0.600000000000 1677099 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": 1190592, "vin": [ { "gen": { "height": 1190582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d937bda7675e8392c1958cb1f6b25ad3d52ba0960f1ab4b1423bc4b9a9a558f4" } } ], "extra": [ 1, 162, 200, 19, 33, 6, 70, 44, 121, 13, 77, 188, 168, 132, 229, 162, 45, 5, 44, 230, 252, 12, 212, 238, 149, 158, 48, 73, 14, 15, 132, 163, 122, 2, 17, 0, 0, 0, 2, 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