Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75dcc9c947080fd9d7aa4ad414be09074437464d38dfb91f79a676b2b2e6dcbc

Tx prefix hash: 56f6c9972866ff8c8bb0eed6d16d9b83e73fd379166381c7b8d0b5b029f1744c
Tx public key: 91674266cc8c791e1f26c45579514f4662f4dc537a3d57a94be1e996f60965b5
Timestamp: 1750935658 Timestamp [UCT]: 2025-06-26 11:00:58 Age [y:d:h:m:s]: 00:147:17:00:55
Block: 1313135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103555 RingCT/type: yes/0
Extra: 0191674266cc8c791e1f26c45579514f4662f4dc537a3d57a94be1e996f60965b50211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af3826683f1ebdbccda19e52377a34bc0cb4e0660146c24f7f06500db4cb458f 0.600000000000 1800774 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": 1313145, "vin": [ { "gen": { "height": 1313135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af3826683f1ebdbccda19e52377a34bc0cb4e0660146c24f7f06500db4cb458f" } } ], "extra": [ 1, 145, 103, 66, 102, 204, 140, 121, 30, 31, 38, 196, 85, 121, 81, 79, 70, 98, 244, 220, 83, 122, 61, 87, 169, 75, 225, 233, 150, 246, 9, 101, 181, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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