Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559924638f428ee4b96f5b89177b954aed5aa54ce69b569e5c7f6293bdfe85c2

Tx prefix hash: 5c1c439091bea243a7a56a5573e3dd09334440f951bcbe7080c0224662c6ddb9
Tx public key: f0db6cd9929f36bc03eee5643f690c9884dd52a862f8a807d61f8433886cd0fd
Timestamp: 1752579921 Timestamp [UCT]: 2025-07-15 11:45:21 Age [y:d:h:m:s]: 00:122:12:47:30
Block: 1325991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86315 RingCT/type: yes/0
Extra: 01f0db6cd9929f36bc03eee5643f690c9884dd52a862f8a807d61f8433886cd0fd0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de1f49e6e26d7b5f05aabac6268f8a4d1f6cbd8b766c82b7ab8a016b6028373e 0.600000000000 1813740 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": 1326001, "vin": [ { "gen": { "height": 1325991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de1f49e6e26d7b5f05aabac6268f8a4d1f6cbd8b766c82b7ab8a016b6028373e" } } ], "extra": [ 1, 240, 219, 108, 217, 146, 159, 54, 188, 3, 238, 229, 100, 63, 105, 12, 152, 132, 221, 82, 168, 98, 248, 168, 7, 214, 31, 132, 51, 136, 108, 208, 253, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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