Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3420b229f38ffde50dafe2770e5204f37ec587d4b4c732c438362eb8fabcb9a

Tx prefix hash: 7559df1114716e2defa84b062bfd497e0922dcaece79327105b4126f8ef3a456
Tx public key: 35d6121c4e49376ea4a46236b412d8d0c0a866332ab7ebfbc3cce742eab842a8
Timestamp: 1760994615 Timestamp [UCT]: 2025-10-20 21:10:15 Age [y:d:h:m:s]: 00:077:02:40:46
Block: 1394325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55209 RingCT/type: yes/0
Extra: 0135d6121c4e49376ea4a46236b412d8d0c0a866332ab7ebfbc3cce742eab842a80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1ab3aa0fb58bb28be24d2ea4b9a898f805b63a0f19e71273ea14d096c0c8210 0.600000000000 1882596 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": 1394335, "vin": [ { "gen": { "height": 1394325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1ab3aa0fb58bb28be24d2ea4b9a898f805b63a0f19e71273ea14d096c0c8210" } } ], "extra": [ 1, 53, 214, 18, 28, 78, 73, 55, 110, 164, 164, 98, 54, 180, 18, 216, 208, 192, 168, 102, 51, 42, 183, 235, 251, 195, 204, 231, 66, 234, 184, 66, 168, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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