Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23dc9fbf9dad958357e4f2a1a65a6cfd7d31464f44adbc30c9eb57750b7de650

Tx prefix hash: 9d50da90711964a618fb153aa56794931ae50b67a484f23b4c608e88c9dbbe70
Tx public key: af2c3ce9410488a6c2a40a0988a8ee9eec347729f157f4db4028a96456e363b4
Timestamp: 1636270412 Timestamp [UCT]: 2021-11-07 07:33:32 Age [y:d:h:m:s]: 03:190:01:11:32
Block: 369121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914219 RingCT/type: yes/0
Extra: 01af2c3ce9410488a6c2a40a0988a8ee9eec347729f157f4db4028a96456e363b40211000000024f792ffd000000000000000000

1 output(s) for total of 36.723942029000 dcy

stealth address amount amount idx
00: c64f3ea4a156fccdddb65935ea5234ea74534689566ba2a10e5f8f7c8f335fc0 36.723942029000 748533 of 0

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": 369131, "vin": [ { "gen": { "height": 369121 } } ], "vout": [ { "amount": 36723942029, "target": { "key": "c64f3ea4a156fccdddb65935ea5234ea74534689566ba2a10e5f8f7c8f335fc0" } } ], "extra": [ 1, 175, 44, 60, 233, 65, 4, 136, 166, 194, 164, 10, 9, 136, 168, 238, 158, 236, 52, 119, 41, 241, 87, 244, 219, 64, 40, 169, 100, 86, 227, 99, 180, 2, 17, 0, 0, 0, 2, 79, 121, 47, 253, 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