Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 520c22857537e6376f969c6a5c680725fbb0bc4e5a8f61202b18e309848a8907

Tx prefix hash: 12b6f13751e8049ab0e6b98e221afd288b7e6529f476559eb87213e34c0be901
Tx public key: e50ebc76397f4f781fb7c55225a10f929dcc39ef74e8a8d2fab6c9ce353b2209
Timestamp: 1759699141 Timestamp [UCT]: 2025-10-05 21:19:01 Age [y:d:h:m:s]: 00:035:20:35:29
Block: 1383560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25677 RingCT/type: yes/0
Extra: 01e50ebc76397f4f781fb7c55225a10f929dcc39ef74e8a8d2fab6c9ce353b2209021100000007a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c7c5a4efb225c4db263b3ce144fc8a94274e680e395082b8c4d586813fd09bd 0.600000000000 1871707 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": 1383570, "vin": [ { "gen": { "height": 1383560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c7c5a4efb225c4db263b3ce144fc8a94274e680e395082b8c4d586813fd09bd" } } ], "extra": [ 1, 229, 14, 188, 118, 57, 127, 79, 120, 31, 183, 197, 82, 37, 161, 15, 146, 157, 204, 57, 239, 116, 232, 168, 210, 250, 182, 201, 206, 53, 59, 34, 9, 2, 17, 0, 0, 0, 7, 165, 220, 205, 121, 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