Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d2f9775b1d66ba729d103f855775e65776c6614c056f1220bd468134fdc7db

Tx prefix hash: 8ee538e8d88f2912ebfbc67a97cada37d6d2e186fc1b7324ec8bbac00d3868da
Tx public key: 58f6a9f94493851cd9193ed62a20d3b1a58aefd8a010f1eaa1f83876731e7e50
Timestamp: 1712349871 Timestamp [UCT]: 2024-04-05 20:44:31 Age [y:d:h:m:s]: 01:012:10:35:27
Block: 994101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269886 RingCT/type: yes/0
Extra: 0158f6a9f94493851cd9193ed62a20d3b1a58aefd8a010f1eaa1f83876731e7e500211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad81804905b0fd07189b371ed14604da84fcc429f4cdad950e492de01a0e6fcd 0.600000000000 1454501 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": 994111, "vin": [ { "gen": { "height": 994101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad81804905b0fd07189b371ed14604da84fcc429f4cdad950e492de01a0e6fcd" } } ], "extra": [ 1, 88, 246, 169, 249, 68, 147, 133, 28, 217, 25, 62, 214, 42, 32, 211, 177, 165, 138, 239, 216, 160, 16, 241, 234, 161, 248, 56, 118, 115, 30, 126, 80, 2, 17, 0, 0, 0, 3, 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