Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58ac93a2462b844c5ad417b98a18e50634c280214459b9c305b3db4fa07e72de

Tx prefix hash: 59ec259d80da29576b7fe3d53e37b1f1779b1a6eceeb4d0fb5dde0d102c47d9b
Tx public key: efe0b90475e83d6a2899f6496f67b6333cbd68a6c51f04c273e03539d8664101
Timestamp: 1757095056 Timestamp [UCT]: 2025-09-05 17:57:36 Age [y:d:h:m:s]: 00:063:13:59:22
Block: 1362058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45457 RingCT/type: yes/0
Extra: 01efe0b90475e83d6a2899f6496f67b6333cbd68a6c51f04c273e03539d866410102110000000bb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8627465bc83add5ed9779aa76b9e1dc9c1c65342ac7a8063c5d5db4720dce6a 0.600000000000 1850081 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": 1362068, "vin": [ { "gen": { "height": 1362058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8627465bc83add5ed9779aa76b9e1dc9c1c65342ac7a8063c5d5db4720dce6a" } } ], "extra": [ 1, 239, 224, 185, 4, 117, 232, 61, 106, 40, 153, 246, 73, 111, 103, 182, 51, 60, 189, 104, 166, 197, 31, 4, 194, 115, 224, 53, 57, 216, 102, 65, 1, 2, 17, 0, 0, 0, 11, 178, 247, 132, 196, 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