Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2087f0eb91abbb93a495533e412cdcb182100442e13f9b82143d81f10e8ae6

Tx prefix hash: 01902392bd9a2f5f1fb7975db5400b7a36319b62f98df5b5325c08edb8910152
Tx public key: eea7d97690c531e7fe52e9cbde09579fc002658405b58600d8212b847158b2a2
Timestamp: 1759738024 Timestamp [UCT]: 2025-10-06 08:07:04 Age [y:d:h:m:s]: 00:052:23:08:18
Block: 1383888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37923 RingCT/type: yes/0
Extra: 01eea7d97690c531e7fe52e9cbde09579fc002658405b58600d8212b847158b2a2021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83d0a8a0fc6f8c48db41bde79424f0e08ab76ae59c386b7fa6435ae53d39e2c7 0.600000000000 1872037 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": 1383898, "vin": [ { "gen": { "height": 1383888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83d0a8a0fc6f8c48db41bde79424f0e08ab76ae59c386b7fa6435ae53d39e2c7" } } ], "extra": [ 1, 238, 167, 217, 118, 144, 197, 49, 231, 254, 82, 233, 203, 222, 9, 87, 159, 192, 2, 101, 132, 5, 181, 134, 0, 216, 33, 43, 132, 113, 88, 178, 162, 2, 17, 0, 0, 0, 4, 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