Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d41313fc3b722ad6c0f1b8e6e9f88026c2de90e08e0fb268e15433dd4eedc00

Tx prefix hash: dd09aafbecc961999c5870c939836892f06aaed723b445a87afab7f692c32d7b
Tx public key: 33b6dc94f37df141420f538112a3b2ffb75ad249f7625039ad4c980ceabd40c8
Timestamp: 1711214650 Timestamp [UCT]: 2024-03-23 17:24:10 Age [y:d:h:m:s]: 01:016:01:05:49
Block: 984746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272412 RingCT/type: yes/0
Extra: 0133b6dc94f37df141420f538112a3b2ffb75ad249f7625039ad4c980ceabd40c80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1858047b1037c087166d36f12c6ee0d3c7e4df0af6cd943642aa74e138d3de8a 0.600000000000 1444919 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": 984756, "vin": [ { "gen": { "height": 984746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1858047b1037c087166d36f12c6ee0d3c7e4df0af6cd943642aa74e138d3de8a" } } ], "extra": [ 1, 51, 182, 220, 148, 243, 125, 241, 65, 66, 15, 83, 129, 18, 163, 178, 255, 183, 90, 210, 73, 247, 98, 80, 57, 173, 76, 152, 12, 234, 189, 64, 200, 2, 17, 0, 0, 0, 2, 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