Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad50f545db2923159dc9d5038d08632efae637c1a44e72e1eff6df73ea363070

Tx prefix hash: 0aa1e8bde34188bb17342a3dd0d87952f1e79bee3fff0e5a52dc0f1be29cd79a
Tx public key: 52182024503cf79d869a168f563a1de2f2acd34de59b18c935e3d2fa28c9ef29
Timestamp: 1718269411 Timestamp [UCT]: 2024-06-13 09:03:31 Age [y:d:h:m:s]: 00:282:15:34:35
Block: 1043214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201975 RingCT/type: yes/0
Extra: 0152182024503cf79d869a168f563a1de2f2acd34de59b18c935e3d2fa28c9ef290211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8834afbe5ad2247e888d7a5fdea6fbb074cd87be554b2f23a0e9ef4fe1a8cc42 0.600000000000 1512311 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": 1043224, "vin": [ { "gen": { "height": 1043214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8834afbe5ad2247e888d7a5fdea6fbb074cd87be554b2f23a0e9ef4fe1a8cc42" } } ], "extra": [ 1, 82, 24, 32, 36, 80, 60, 247, 157, 134, 154, 22, 143, 86, 58, 29, 226, 242, 172, 211, 77, 229, 155, 24, 201, 53, 227, 210, 250, 40, 201, 239, 41, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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