Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca8dbf6d6ef20145d99d78534d724db42f5342ec168a33eeaadc41422a47a6a

Tx prefix hash: 690d5df3526d645b3a9e0963225301e629da1acd3d52d2d1983f5d78249a9dc3
Tx public key: e4055069eb09287d3ff2a884daeb63e1744f2798b22ad39922971aac12abcfb3
Timestamp: 1707137254 Timestamp [UCT]: 2024-02-05 12:47:34 Age [y:d:h:m:s]: 01:337:21:58:07
Block: 950903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500374 RingCT/type: yes/0
Extra: 01e4055069eb09287d3ff2a884daeb63e1744f2798b22ad39922971aac12abcfb3021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c03869f1e2cf48b7ddaaec99f0f74b841ae60b515ebcae53081e75e9caa51fd4 0.600000000000 1409593 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": 950913, "vin": [ { "gen": { "height": 950903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c03869f1e2cf48b7ddaaec99f0f74b841ae60b515ebcae53081e75e9caa51fd4" } } ], "extra": [ 1, 228, 5, 80, 105, 235, 9, 40, 125, 63, 242, 168, 132, 218, 235, 99, 225, 116, 79, 39, 152, 178, 42, 211, 153, 34, 151, 26, 172, 18, 171, 207, 179, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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