Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7e5130f15e639cd206eeff3e4acd81e254d99d189ac2a2183d378388361b66c

Tx prefix hash: d2360a6ab83bf025081fea223d52c517eb5b979872d84689b9077fff008dcd88
Tx public key: 3c76938bf9e20675d0853f94b62205ce274d4a2b92ccc1d3e4719c401244b905
Timestamp: 1715149638 Timestamp [UCT]: 2024-05-08 06:27:18 Age [y:d:h:m:s]: 00:261:11:05:26
Block: 1017349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187080 RingCT/type: yes/0
Extra: 013c76938bf9e20675d0853f94b62205ce274d4a2b92ccc1d3e4719c401244b9050211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e45e9b1f87096b53dc5320024e7b3cae0e997e509f9f94e8be56e290c49efc 0.600000000000 1481124 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": 1017359, "vin": [ { "gen": { "height": 1017349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e45e9b1f87096b53dc5320024e7b3cae0e997e509f9f94e8be56e290c49efc" } } ], "extra": [ 1, 60, 118, 147, 139, 249, 226, 6, 117, 208, 133, 63, 148, 182, 34, 5, 206, 39, 77, 74, 43, 146, 204, 193, 211, 228, 113, 156, 64, 18, 68, 185, 5, 2, 17, 0, 0, 0, 1, 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