Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798a6119600806e03afcb7851e728c05e5849758c4c8a4776ac09da1e4913bb6

Tx prefix hash: 946281c0401da26061b83378f36e13cafbfb427402df667269d05369f0ddc54d
Tx public key: 35b271e8f2dbf6e7d532fa2f2938fb4102ac9e4dbea350df021e4c4ec7394bc8
Timestamp: 1740889768 Timestamp [UCT]: 2025-03-02 04:29:28 Age [y:d:h:m:s]: 00:262:05:08:49
Block: 1230270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185162 RingCT/type: yes/0
Extra: 0135b271e8f2dbf6e7d532fa2f2938fb4102ac9e4dbea350df021e4c4ec7394bc80211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab6c65545f2ae2a67ba43622eb497bafa5e97fa75d48128cfc02f836cd6a808b 0.600000000000 1717167 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": 1230280, "vin": [ { "gen": { "height": 1230270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab6c65545f2ae2a67ba43622eb497bafa5e97fa75d48128cfc02f836cd6a808b" } } ], "extra": [ 1, 53, 178, 113, 232, 242, 219, 246, 231, 213, 50, 250, 47, 41, 56, 251, 65, 2, 172, 158, 77, 190, 163, 80, 223, 2, 30, 76, 78, 199, 57, 75, 200, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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