Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b14f58a101f9c2d35a9267b26cd6bde04912379573d72f072f9f3954a2c29e3

Tx prefix hash: 63afe3ccf58b5faccfff80e04c37de1173c28c378a1e7e32edbb98fac1e8c705
Tx public key: bfff949695344682985485f3bdc1e729e454ddd55c1c760a59a3a54878f1480b
Timestamp: 1584526706 Timestamp [UCT]: 2020-03-18 10:18:26 Age [y:d:h:m:s]: 04:303:20:51:13
Block: 84898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112822 RingCT/type: yes/0
Extra: 01bfff949695344682985485f3bdc1e729e454ddd55c1c760a59a3a54878f1480b0211000000028e8a0ce2000000000000000000

1 output(s) for total of 321.143004333000 dcy

stealth address amount amount idx
00: 2da2cee6c207ef3c823aea77062f1eada704fdb5174e297b2caa433e2a46df92 321.143004333000 153670 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": 84908, "vin": [ { "gen": { "height": 84898 } } ], "vout": [ { "amount": 321143004333, "target": { "key": "2da2cee6c207ef3c823aea77062f1eada704fdb5174e297b2caa433e2a46df92" } } ], "extra": [ 1, 191, 255, 148, 150, 149, 52, 70, 130, 152, 84, 133, 243, 189, 193, 231, 41, 228, 84, 221, 213, 92, 28, 118, 10, 89, 163, 165, 72, 120, 241, 72, 11, 2, 17, 0, 0, 0, 2, 142, 138, 12, 226, 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