Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 761dfe1cd1a6017c8529062b0dcdf1cf6adfd0d5d3e87640f559305c12e06435

Tx prefix hash: 6109f2a7be2f14e5d32225fcfae8b8a3c7ab28f24744b636ac4a5cda7b17d053
Tx public key: 36111b3a62a5be523c912444baa7c1409623d54de49d54ad3fce0603e01813ca
Timestamp: 1753081290 Timestamp [UCT]: 2025-07-21 07:01:30 Age [y:d:h:m:s]: 00:078:13:56:23
Block: 1330067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54910 RingCT/type: yes/0
Extra: 0136111b3a62a5be523c912444baa7c1409623d54de49d54ad3fce0603e01813ca021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f475da75bf354b3a276ef4d1527a1c3024e15326d6daeb87e3e71e1072588b5 0.600000000000 1817858 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": 1330077, "vin": [ { "gen": { "height": 1330067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f475da75bf354b3a276ef4d1527a1c3024e15326d6daeb87e3e71e1072588b5" } } ], "extra": [ 1, 54, 17, 27, 58, 98, 165, 190, 82, 60, 145, 36, 68, 186, 167, 193, 64, 150, 35, 213, 77, 228, 157, 84, 173, 63, 206, 6, 3, 224, 24, 19, 202, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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